The "Build assets artifact" workflow only uploaded built assets as ephemeral GitHub Actions artifacts, with no automatic attachment to GitHub releases on version tags.

Changes

• New triggers: Workflow now runs on v*.*.* and v*.*.*-** tag pushes (matching the Docker build workflow pattern)
• Scoped permissions: Workflow-level contents permission stays read; added contents: write at the job level to limit blast radius for branch/PR runs
• Release upload step: Conditional step uploads both zip files as release assets when triggered by a tag:

- name: Upload assets as release attachment
  if: startsWith(github.ref, 'refs/tags/')
  run: |
    gh release upload "${{ github.ref_name }}" /tmp/partdb_assets.zip /tmp/partdb_with_assets.zip --clobber
  env:
    GH_TOKEN: ${{ github.token }}

--clobber allows re-running the workflow without manual cleanup if assets were already uploaded.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.